release: 0.80.0#132
Open
stainless-app[bot] wants to merge 3 commits into
Open
Conversation
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sun, 16 Aug 2026 00:06:12 GMT |
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 17, 2026 00:05
d271a1e to
e81799d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.80.0 (2026-07-17)
Full Changelog: v0.79.0...v0.80.0
Features
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Note
Medium Risk
Adds optional managed-auth submit and response shapes on login flows; changes are additive but integrators driving auth should verify both legacy and canonical paths against the API.
Overview
Release 0.80.0 bumps package version metadata and refreshes the pinned OpenAPI spec used for codegen.
The substantive SDK change is managed auth canonical flow support for CUA-style workers.
auth.connections.submitgains optionalfield_values(field ID → value) andselected_choice_idfor stable IDs instead of legacy name/selector-based submit.ManagedAuthand SSEManagedAuthStateEventresponses addfieldsandchoicesmodels (withChoice/Fieldtypes); docs say clients should prefer these overdiscovered_fields,mfa_options,pending_sso_buttons, andsign_in_optionswhen present. Legacy submit params remain unchanged.Proxy
checktests now useurl="https://example.com"so generated API reference examples show a realistic URL.Reviewed by Cursor Bugbot for commit e81799d. Bugbot is set up for automated code reviews on this repo. Configure here.